Multimodal conversation transfer

ABSTRACT

In one embodiment, a user may transfer a multimodal conversation. A multimodal conversation may have a first mode communication session and a second mode communication session. A first user point of presence may execute a first transfer of the first mode communication session with a first partner point of presence from the first user point of presence to a first target point of presence. A second user point of presence may execute a second transfer of the second mode communication session with a second partner point of presence from the second user point of presence to a second target point of presence.

RELATED APPLICATION(S)

This application is a Continuation of, and claims benefit from, U.S.patent application Ser. No. 12/146,428 that was filed on Jun. 25, 2008,and that is incorporated herein by reference in its entirety.

BACKGROUND

A personal computer that integrates internet functionality may be usedto greatly increase the ability of a user to communicate across severalmodalities. A user may contact a communication partner using electronicmail, or e-mail, in which a discrete set of text may be sent from theuser to the communication partner at a time convenient to an e-mailserver. The user may associate a file or application with the text,sending the file or application as an attachment to the e-mail. A usermay enact a real-time conversation with a communication partner usinginstant messaging, in which sets of text may be exchanged between theuser and the communication partner instantaneously.

The personal computer that integrates internet functionality mayintegrate services normally associated with other devices. A personalcomputer with audio input and output capability may be modified bysoftware to act as a telephone for the user. The user may exchangereal-time audio data with a communication partner, allowing aconversation to take place. Further, a personal computer with digitalimage capturing capability may act as a video telephone. A user and acommunication partner may exchange synchronized video and audio data,allowing a greater flexibility in the types of communications that maytake place.

Many existing communication technologies may integrate these computinginnovations. One example would be the internet protocol (IP) telephone.An IP telephone may use voice over IP (VOIP) to transmit telephone callsover the internet, rather than a public switched telephone network.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that is further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

Embodiments discussed below relate to transferring conversations thatmay occur across multiple modalities, such as instant messaging, voice,video, and other conversational modalities. A first user point ofpresence may execute a first transfer of a first mode communicationsession with a first partner point of presence from the first user pointof presence to a first target point of presence. A second user point ofpresence may execute a second transfer of a second mode communicationsession with a second partner point of presence from the second userpoint of presence to a second target point of presence.

DRAWINGS

In order to describe the manner in which the above-recited and otheradvantages and features can be obtained, a more particular descriptionis described below and will be rendered by reference to specificembodiments thereof which are illustrated in the appended drawings.Understanding that these drawings depict only typical embodiments andare not therefore to be considered to be limiting of its scope,implementations will be described and explained with additionalspecificity and detail through the use of the accompanying drawings.

FIG. 1 illustrates a block diagram of an exemplary communication devicethat may be used in multimodal conversations.

FIG. 2 illustrates, in a block diagram, one embodiment of a set ofpaired communication devices.

FIGS. 3 a-b illustrate, in block diagrams, two embodiments of amultimodal conversation using a user communication system.

FIG. 4 illustrates, in a flowchart, one method of transferring amultimodal conversation.

FIG. 5 illustrates, in a flowchart, one method of transferring amultimodal conversation using a communication server.

FIG. 6 illustrates, in a call flow diagram, one embodiment of a methodfor a user initiated, target completed multimodal call transfer.

FIG. 7 illustrates, in a call flow diagram, one embodiment of a methodfor a user controlled multimodal call transfer.

FIG. 8 illustrates, in a call flow diagram, one embodiment of a methodfor independent endpoint multimodal call transfer.

DETAILED DESCRIPTION

Embodiments are discussed in detail below. While specificimplementations are discussed, it should be understood that this is donefor illustration purposes only. A person skilled in the relevant artwill recognize that other components and configurations may be usedwithout parting from the spirit and scope of the subject matter of thisdisclosure.

A multimodal conversation may be a single conversation using multiplecommunication sessions each having a different communication mode, suchas instant messaging (IM), telephone, video, and other communicationmodes. The multimodal conversation may have a single conversationidentifier (CID) associated with each communication session of themultimodal conversation.

A user may have multiple points of presence (NMPOP) on a communicationnetwork. A point of presence may refer to an endpoint by which a usercontrols and interacts with the user's end of a communication session.The user may have MPOP represented by a single communication devicecapable of communicating over multiple communication modes, such as apersonal computer executing a communication software package capable ofIM, voice, video conferencing, application sharing, and othercommunication modes. The user may also have MPOP represented byassociating multiple communication devices with a single user, such as apersonal computer, an internet telephone, a personal texting device, andother communication devices. Multiple communication devices may be“paired” together to execute multimodal conversations. Pairing thecommunication devices allows a user to use a single communication deviceto control other communication devices representing the MPOP of thatuser.

A multimodal conversation may have a first communication session havinga first communication mode and a second communication session having asecond communication mode. A first user point of presence may execute afirst transfer of the first communication session with a first partnerpoint of presence from the first user point of presence to a firsttarget point of presence. A second user point of presence may execute asecond transfer of the second communication with a second partner pointof presence from the second user point of presence to a second targetpoint of presence.

FIG. 1 illustrates a block diagram of an exemplary communication device100 which may be used in multimodal communications. Communication device100 may be a personal computer, laptop, an internet protocol (IP)telephone, or other communication device capable of acting as anindependent communication device. Communication device 100 may include abus 110, a processor 120, a memory 130, a read only memory (ROM) 140, astorage device 150, an input device 160, an output device 170, and acommunication interface 180. Bus 110 may permit communication among thecomponents of communication device 100.

Processor 120 may include at least one conventional processor ormicroprocessor that interprets and executes a set of instructions.Memory 130 may be a random access memory (RAM) or another type ofdynamic storage device that stores information and instructions forexecution by processor 120. Memory 130 may also store temporaryvariables or other intermediate information used during execution ofinstructions by processor 120. ROM 140 may include a conventional ROMdevice or another type of static storage device that stores staticinformation and instructions for processor 120. Storage device 150 mayinclude any type of tangible machine-readable medium, such as, forexample, magnetic or optical recording media and its correspondingdrive.

Input device 160 may include one or more conventional mechanisms thatpermit a user to input information to communication device 100, such asa keyboard, a mouse, a voice recognition device, a microphone, aheadset, etc. Output device 170 may include one or more conventionalmechanisms that output information to the user, including a display, aprinter, one or more speakers, a headset, or a medium, such as a memory,or a magnetic or optical disk and a corresponding disk drive.Communication interface 180 may include any transceiver-like mechanismthat enables processing device 100 to communicate with other devices ornetworks. Communication interface 180 may include a network interface ora pairing interface. The interface may be a wireless, wired, or opticalinterface. In one embodiment, the interface may include a universalserial bus (USB) interface, a Bluetooth® interface, or other suchinterface that may be used to attach peripheral devices or pair othercommunication devices.

Communication device 100 may perform such functions in response toprocessor 120 executing sequences of instructions contained in acomputer-readable medium, such as, for example, memory 130, a magneticdisk, or an optical disk. Such instructions may be read into memory 130from another computer-readable medium, such as storage device 150, orfrom a separate device via communication interface 180.

Each communication device associated with a user may act as a point ofpresence for that user. Multiple communication devices may be moreeasily managed by “pairing”. FIG. 2 illustrates in a block diagram oneembodiment of a set 200 of paired communication devices. A servercommunication device (SCD) 210 may be a communication device that mayact as a server and may directly connect with another communicationdevice. SCD 210 may be an internet protocol (IP) telephone, a computer,or other communication device that may independently create acommunication link with another communication device. SCD 210 mayexecute a server-side unified communications software application thatcreates a call connection with another communication device using apeer-to-peer protocol.

A controller communication device (CCD) 220 may be a communicationsdevice that may act as a controller for SCD 210. CCD 220 may act as anindependent communication device, capable of setting up a communicationslink independent of SCD 210. CCD 220 may be an IP telephone, a computer,or other independent communication device. CCD 220 may execute aclient-side unified communication software application that enablescontrol of SCD 210.

CCD 220 may pair 230 with SCD 210 using a variety of techniques. CCD 220may create a data link with SCD 210 using a universal serial bus (USB)connection, an Ethernet connection, a Bluetooth® connection, or othertype of data connection. A communication software program executed byCCD 220 may then interact with a communication software program executedby SCD 210. SCD 210 and CCD 220 may act as an integrated system oncepaired. SCD 210 may act as CCD 220 in one instance and SCD 210 in adifferent instance, and vice versa. CCD 220 may eschew an intermediaryserver when pairing directly with SCD 210. CCD 220 may use a third partycontrol protocol (TPCP) to observe, initiate, and control sessionsbetween CCD 220 and any remote device connected to SCD 210.

While SCD 210 and CCD 220 are referred to as being “paired” 230, morethan two devices may be associated with each other. For example, anancillary communication device (ACD) 240 may be paired with SCD 210 andCCD 220. ACD 240 may be an IP telephone, computer, or othercommunication device that may execute a communication mode over acommunication connection.

FIG. 3 a illustrates, in a block diagram, one embodiment of a multimodalconversation 300 using a user communication system having communicationdevices capable of multiple modes of communication. A multimodalconversation 300 may be associated with a CID 302, in order to moreefficiently manage each mode of the multimodal conversation 300.Multimodal conversation 300 may have a first mode communication session(MCS) 304 and a second MCS 306. Although two communication sessions withdifferent modes for a single multimodal conversation are described, amultimodal conversation may have any number of communication sessionseach having a different communication mode. Each MCS may operate indifferent modes, such as IM, telephone conversation, applicationsharing, video conferencing, or other modes of communication. Each MCSof the multimodal conversation 300 may be associated with the same CID302.

A user may be associated with a first user point of presence (UPOP) 308to interact with first MCS 304 and a second UPOP 310 to interact withsecond MCS 306. A single user communication device (UCD) 312, capable ofperforming multiple modes of communication, may execute both first UPOP308 and second UPOP 310. The user may seek to create a communicationlink with a communication partner. The communication partner may beassociated with a first partner point of presence (PPOP) 314 to interactwith first MCS 304 and a second PPOP 316 to interact with second MCS306. A single partner communication device (PCD) 318, capable ofperforming multiple modes of communication, may execute both first PPOP314 and second PPOP 316.

The user or the communication partner may transfer a communicationsession between the user and communication partner to a transfer target.The transfer target may be associated with a first target point ofpresence (TPOP) 320 to interact with first MCS 304 and a second TPOP 322to interact with second MCS 306. A single target communication device(TCD) 324, capable of performing multiple modes of communication, mayexecute both first TPOP 320 and second TPOP 322. First UPOP 308 maydirectly transfer the first MCS 304 to first TPOP 320 and second UPOP310 may directly transfer the second MCS 306 to second TPOP 322regardless of whether the multimodal conversation was initiated by theuser or the communication partner.

FIG. 3 b illustrates, in a block diagram, one embodiment of a multimodalconversation 350 using a user communication system having pairedcommunication devices, with each device capable of a different mode ofcommunication. The user may be associated with a user CCD (UCCD) 352,acting as first UPOP 308, and a user SCD (USCD) 354, acting as secondUPOP 310. The communication partner may be associated with a partner CCD(PCCD) 356, acting as first PPOP 314, and a partner SCD (PSCD) 358,acting as second PPOP 316. The transfer target may be associated with atarget CCD (TCCD) 360, acting as first TPOP 320, and a target SCD (TSCD)362, acting as second TPOP 322.

FIG. 4 illustrates, in a flowchart, one method 400 of transferring amultimodal conversation. The user may track a multimodal conversation byCID 302. First UPOP 308 may execute a first MCS 304 with first PPOP 314(Block 402). Second UPOP 310 may execute a second MCS 306 with secondPPOP 316. Alternately, if first UPOP 308 resides on UCCD 352 and secondUPOP 310 resides on USCD 354, UCCD 352 may direct USCD 354 to executethe second MCS 306 between second UPOP 310 and second PPOP 316 (Block404). Upon deciding to transfer the communication sessions, the user mayexecute a consultation with a transfer target communication partner(Block 406). The transfer target communication partner may be associatedwith first TPOP 320 and second TPOP 322 on TCD 324. Alternately, thetransfer target communication partner may be associated with first TPOP320 on TCCD 360 and second TPOP 324 on TSCD 362. The consultation may bewith the transfer target communication partner via first TPOP 320 orsecond TPOP 322. Upon approval by the transfer target communicationpartner, first UPOP 308 may execute a first transfer of the first MCS304 to first TPOP 320 (Block 408).

First UPOP 308 may alert first TPOP 322 of the second MCS 306 (Block410). First UPOP 308 may determine the mode capability of second TPOP322, to see if second TPOP 322 is capable of executing a second MCS 306(Block 412). First UPOP 308 may check the mode capability by asking thetransfer target communication partner during the consultation process,by including the query in the invitation message for the firstcommunication session, by making a connection attempt with second TPOP322, or by some other method. If second TPOP 322 is capable of executingsecond MCS 306 (Block 414), then first UPOP 308 may execute a secondtransfer of second MCS 306 to second TPOP 322 (Block 416). If secondTPOP 322 is incapable of executing second MCS 306 (Block 414) and asuitable alternate communication mode is available (Block 418), thensecond UPOP 310 may switch second MCS 306 to an alternate modecommunication session (Block 420). First UPOP 308 may then execute asecond transfer of second MCS 306 to second TPOP 322 (Block 416). If noalternate mode is available (Block 418), then first UPOP 308 may dropsecond MCS 306 (Block 422).

First UPOP 308 may use a separate conference server to transfer firstMCS 304 and second MCS 306. FIG. 5 illustrates, in a flowchart, onemethod 500 of transferring a multimodal conversation using a conferenceserver. The conference server may connect to first MCS 304 and secondMCS 306 (Block 502). The conference server may part the different modesof the multimodal conversation by assigning a first mode CID (MCID) tofirst MCS 304 and a second MCID to second MCS 306 (Block 504). Theconference server may invite first TPOP 320 to join first MCS 304 andsecond TPOP 322 to join second MCS 306 (Block 506). Once the conferenceserver detects first TPOP 320 connecting with first MCS 304 and secondTPOP 322 connecting with second TPOP 306 (Block 508), the conferenceserver may reassign a new CID to first MCS 304 and second MCS 306 (Block510). The conference server may then sever its connection with first MCS304 and second MCS 306 (Block 512).

First UPOP 308 may transfer a communication session using a variety ofmethods. FIG. 6 illustrates, in a call flow diagram, one embodiment of amethod 600 for a user initiated, target completed multimodal calltransfer. A user may transfer a multimodal conversation between the userand a communication partner to a transfer-target TCD 324 may executeboth a first TPOP 320 and a second TPOP 322. UCCD 352, or first UPOP308, may have an IM communication session 602 established with PCCD 356,or first PPOP 314. USCD 354, or second UPOP 310, may have a real timeprotocol (RTP) call communication session 604 established with PSCD 358,or second PPOP 316. The user may initiate a transfer action 606 to thetransfer target. UCCD 352 may send a session initiation protocol (SIP)REFER message 608 to PCCD 356. REFER message 608 may have a headerlisting, in addition to the transfer target, a set of transfer data forthe call communication session 604, including a communication mode, anda set of uniform resource identifiers (URIs), such as a global routableuser agent (UA) URI (GRUU) for a device, a CID identifying the connectedcall sessions, a source tag, and a target tag. PCCD 356 may send an“Accepted” message 610 to UCCD 352 upon receipt of REFER message 608.PCCD 356 may send an SIP INVITE message 612 to TCD 324. INVITE message612 may have the same header information as REFER message 608. If thetransfer-target initiates an acceptance action 614, TCD 324 may send anOK message 616 to PCCD 356, which PCCD 356 may respond to with anacknowledgement (ACK) message 618. PCCD 356 may now have an IMcommunication session 620 with TCD 324. PCCD 356 may now sever the IMcommunication session 602 with UCCD 352 with a BYE message 622, whichUCCD 352 may acknowledge with an OK message 624. TCD 324 may initiate asecond communication session by sending an SIP INVITE message 626 toPSCD 358. INVITE message 626 may have a header listing a replacementcall ID, a replacement source rag, a replacement target rag, and otherrouting data. PSCD 358 may accept INVITE message 626 by sending an OKmessage 628 to TCD 324, which TCD 324 may acknowledge with an ACKmessage 630. PSCD 358 may now sever the call communication session 604with USCD 354 with a BYE message 632, which USCD 354 may acknowledgewith an OK message 634. PSCD 358 may now have a RTP call communicationsession 636 with TCD 324.

A single point may be master of all the communication sessions or may becontrolling the other communication session through a remote callcontrol protocol. FIG. 7 illustrates, in a call flow diagram, oneembodiment of a method 700 for a user point of preference controlledmultimodal call transfer. UCCD 352 may have an IM communication session702 established with PCCD 356. USCD 354 may have a RTP callcommunication session 704 established with PSCD 358. The user mayinitiate a transfer action 706 to the transfer target. UCCD 352 may senda SIP REFER message 708 to the PCCD 356. REFER message 708 may have aheader listing the transfer target. PCCD 356 may send an “Accepted”message 710 to UCCD 352 upon receipt of REFER message 708. PCCD 356 maysend an SIP INVITE message 712 to TCD 324. INVITE message 712 may havethe same target information as REFER message 708. UCCD 352 may send aSIP REFER message 714 to PSCD 358. REFER message 714 may have a headerlisting the transfer target, a call ID, a source tag, and a target tag.PSCD 358 may send an “Accepted” message 716 to UCCD 352 upon receipt ofREFER message 714. PSCD 358 may send an SIP INVITE message 718 to TCD324. INVITE message 718 may have a header listing target information andcommunication mode. TCD 324 may execute a display action 720 to displayto the user a merged control panel for controlling all the communicationsessions associated with the call ID. TCD 324 may accept INVITE message718 by sending an OK message 722 to PSCD 358, which PSCD 358 may respondto with an ACK message 724. TCD 324 may accept INVITE message 712 bysending an OK message 726 to PCCD 356, which PCCD 356 may respond towith an ACK message 728. TCD 324 may now have an IM communicationsession 730 with PCCD 356 while having a RTP call communication session732 with PSCD 358. PSCD 358 may now sever the call communication session704 with USCD 354 with a BYE message 734, which USCD 354 may acknowledgewith an OK message 736. PCCD 356 may now sever the IM communicationsession 702 with UCCD 352 with a BYE message 738, which UCCD 352 mayacknowledge with an OK message 740.

The endpoints in a communication session may act independently. Eachendpoint may be equipped with a conversation state package. Aconversation state pack may be a software application to monitor andmaintain status information about the multimodal conversation so thateach point of presence may act accordingly. FIG. 8 illustrates, in acall flow diagram, one embodiment of a method 800 for independentendpoint multimodal call transfer. UCCD 352 may have an IM communicationsession 802 established with PCCD 356. USCD 354 may have a RTP callcommunication session 804 established with PSCD 358. The user mayinitiate a transfer action 806 to the transfer target. A conversationstate package on the USCD 354 may execute an identification action 808to determine that a transfer action 806 is underway, so that USCD 354may commence its own transfer action as a result. UCCD 352 may send aSIP REFER message 810 to the PCCD 356. REFER message 810 may have aheader listing the transfer target. PCCD 356 may send an “Accepted”message 812 to UCCD 352 upon receipt of REFER message 810. PCCD 356 maysend an SIP INVITE message 814 to TCD 324. INVITE message 814 may havethe same target information as REFER message 810. USCD 354 may send aSIP REFER message 816 to PSCD 358. REFER message 816 may have a headerlisting the transfer target. PSCD 358 may send an “Accepted” message 818to UCCD 352 upon receipt of REFER message 816. PSCD 358 may send an SIPINVITE message 820 to TCD 324. INVITE message 820 may have a headerlisting target information and communication mode. TCD 324 may execute adisplay action 822 to display to the user a merged control panel forcontrolling all the communication sessions associated with the call ID.TCD 324 may accept INVITE message 820 by sending an OK message 824 toPSCD 358, which PSCD 358 may respond to with an ACK message 826. TCD 324may accept INVITE message 814 by sending an OK message 828 to PCCD 356,which PCCD 356 may respond to with an ACK message 830. TCD 324 may nowhave an IM communication session 832 with PCCD 356 while having a RTPcall communication session 834 with PSCD 358. PSCD 358 may now sever thecall communication session 804 with USCD 354 with a BYE message 836,which USCD 354 may acknowledge with an OK message 838. PCCD 356 may nowsever the IM communication session 802 with UCCD 352 with a BYE message840, which UCCD 352 may acknowledge with an OK message 842.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter in the appended claims is not necessarilylimited to the specific features or acts described above. Rather, thespecific features and acts described above are disclosed as exampleforms for implementing the claims.

Although the above description may contain specific derails, they shouldnot be construed as limiting the claims in any way. Other configurationsof the described embodiments are part of the scope of the disclosure.For example, the principles of the disclosure may be applied to eachindividual user where each user may individually deploy such a system.This enables each user to utilize the benefits of the disclosure even ifany one of a large number of possible applications do not use thefunctionality described herein. Multiple instances of electronic deviceseach may process the content in various possible ways. Implementationsare not necessarily in one system used by all end users. Accordingly,the appended claims and their legal equivalents should only define theinvention, rather than any specific examples given.

We claim:
 1. A method performed on a computing device that includes aprocessor and memory, the method comprising: transferring, by thecomputing device from a first device to a second device, a multimodalconversation with the computing device, where the multimodalconversation includes a plurality of communication sessions, where eachof the plurality of communication sessions has a mode that is differentthan the modes of others of the plurality of communication sessions. 2.The method of claim 1 where the transferring the multimodal conversationcomprises transferring, by the computing device, each of the pluralityof communication sessions from the first device to the second device. 3.The method of claim 1 where the transferring comprises switching, by thecomputing device in response to determining that a mode of one of theplurality of communication sessions is not supported by the seconddevice and to determining that an alternate mode is supported by thesecond device, the one of the plurality of communication sessions to thealternate mode.
 4. The method of claim 1 where the transferringcomprises dropping, by the computing device in response to determiningthat a mode of one of the plurality of communication sessions is notsupported by the second device and to determining that an alternate modeis not supported by the second device, the one of the plurality ofcommunication sessions.
 5. The method of claim 1 where the transferringis based on a session initiation protocol (“SIP”).
 6. The method ofclaim 1 where the transferring is in response to results of aconsultation between the computing device and the second device.
 7. Themethod of claim 6 where the consultation comprises determining, by thecomputing device, a mode capability of the second device.
 8. A systemcomprising a computing device and instructions that are togetherconfigured for performing actions, the computing device comprising aprocessor and memory, the actions comprising: transferring, by thecomputing device from a first device to a second device, a multimodalconversation with the computing device, where the multimodalconversation includes a plurality of communication sessions, where eachof the plurality of communication sessions has a mode that is differentthan the modes of others of the plurality of communication sessions. 9.The system of claim 8 where the transferring the multimodal conversationcomprises transferring, by the computing device, each of the pluralityof communication sessions from the first device to the second device.10. The system of claim 8 where the transferring comprises switching, bythe computing device in response to determining that a mode of one ofthe plurality of communication sessions is not supported by the seconddevice and to determining that an alternate mode is supported by thesecond device, the one of the plurality of communication sessions to thealternate mode.
 11. The system of claim 8 where the transferringcomprises dropping, by the computing device in response to determiningthat a mode of one of the plurality of communication sessions is notsupported by the second device and to determining that an alternate modeis not supported by the second device, the one of the plurality ofcommunication sessions.
 12. The system of claim 8 where the transferringis based on a session initiation protocol (“SIP”).
 13. The system ofclaim 8 where the transferring is in response to results of aconsultation between the computing device and the second device.
 14. Thesystem of claim 13 where the consultation comprises determining, by thecomputing device, a mode capability of the second device.
 15. At leastone memory that comprises instructions that, based on execution by aprocessor of a computing device, configure the computing device toperform actions comprising: transferring, by the computing device from afirst device to a second device, a multimodal conversation with thecomputing device, where the multimodal conversation includes a pluralityof communication sessions, where each of the plurality of communicationsessions has a mode that is different than the modes of others of theplurality of communication sessions.
 16. The at least one memory ofclaim 15 where the transferring the multimodal conversation comprisestransferring, by the computing device, each of the plurality ofcommunication sessions from the first device to the second device. 17.The at least one memory of claim 15 where the transferring comprisesswitching, by the computing device in response to determining that amode of one of the plurality of communication sessions is not supportedby the second device and to determining that an alternate mode issupported by the second device, the one of the plurality ofcommunication sessions to the alternate mode.
 18. The at least onememory of claim 15 where the transferring comprises dropping, by thecomputing device in response to determining that a mode of one of theplurality of communication sessions is not supported by the seconddevice and to determining that an alternate mode is not supported by thesecond device, the one of the plurality of communication sessions. 19.The at least one memory of claim 15 where the transferring is based on asession initiation protocol (“SIP”).
 20. The at least one memory ofclaim 15 where the transferring is in response to results of aconsultation between the computing device and the second device, wherethe consultation comprises determining, by the computing device, a modecapability of the second device.